fix(ci): enable noop on agentic workflows to stop IcM page spam#252
Merged
fix(ci): enable noop on agentic workflows to stop IcM page spam#252
Conversation
jbrotsos
approved these changes
Apr 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Three gh-aw agentic workflows (
ci-doctor,msdo-breach-monitor,msdo-issue-assistant) hadsafe-outputs.noop: false. Their prompts instruct the agent to stay silent or callnoopunder various conditions, but with the feature disabled the agent had no way to opt out — so every legitimate silent run was reported as a failure. In this repo, each[aw] ... failedissue opens a CRI IcM ticket that pages on-call. See #247 for the self-perpetuating failure loop.This PR:
safe-outputs.noopon all three workflows (withreport-as-issue: falseso noop calls don't themselves file issues).safe-outputs.report-failure-as-issue: falseas a safety net so edge-case silent exits never page IcM either.msdo-issue-assistantprompt so its existing "don't respond" conditions now direct the agent to callnoopexplicitly, and recognises auto-generated[aw]failure issues..lock.ymlfiles. The gh-aw CLI bundled in v0.61.0 predates the recentactions/github-scriptv9.0.0 bump (fix(ci): bump actions/github-script from 8.0.0 to 9.0.0 #244), so the v9.0.0 SHA was restored after compile to avoid reverting the dependabot update.Validation plan
gh aw compilerecompiles all three workflows cleanly (verified locally)ci-doctordispatch against a successful CI run — expect noop, no issue filedmsdo-breach-monitordispatch with no new CVEs — expect noop, no issue filedmsdo-issue-assistantcomment on an off-topic or[aw]-titled issue — expect no new[aw] ... failedissue, no comment postedmsdo-issue-assistantpositive path: open an MSDO question issue — expect a normal wiki-backed reply witharea:msdo-clilabelDesign docs
Issue #247 will be closed manually once this is merged.